#6276 Improve message parsing for signed message - #6277

there is similar recursive call in

which can cause extension lag for nested signed content. we'll need to implement similar fix there, but let's leave it for separate PR

Got it - Will remember this one and fix it on separate PR after this one.

it's possible for multipart/mixed content to include both signed and unsigned parts. current code stops when it encounters a non-signed node, so it can miss a nested signed node. let’s perform search for another signed node in this case:

const currentSubject = current.headers.subject?.[0]?.value;
fallbackSubject = currentSubject || fallbackSubject;
if (!Mime.isSignedContentNode(current)) {
    const nestedSignedContentNode = Mime.retrieveSignedContentNode([current]);
    if (!nestedSignedContentNode) {
          return fallbackSubject;
    }
    current = nestedSignedContentNode;
    continue;
}

I apologize, I missed that part. I have rechecked it again and fix the said behavior.